|
Fault reporting is a maintenance concept that increases operational availability and that reduces operating cost through three mechanisms. * Reduce labor-intensive diagnostic evaluation * Eliminate diagnostic testing down-time * Provide notification to management for degraded operation This is a prerequisite for Condition-based maintenance.〔(【引用サイトリンク】title=Opnav Instruction 4790.16: Condition Based Maintenance )〕 Active redundancy can be integrated with fault reporting to reduce down time to a few minutes per year. * Passive redundancy * Active redundancy ==History== Formal maintenance philosophies are required by organizations whose primary responsibility is to ensure systems are ready when expected, such as space agencies and military.〔(【引用サイトリンク】title=Opnav Instruction 4790.7: Maintenance Policy for United States Navy Ships )〕 Labor-intensive planned maintenance began during the rise of the industrial revolution. This depends upon periodic diagnostic evaluation based upon calendar dates, distance, or use. The intent is to accomplish diagnostic evaluations that indicate when maintenance is required to prevent inconvenience and safety issues that will occur when critical equipment failures occur during use. The electronic revolution allowed inexpensive sensors and controls to be integrated into most equipment. This includes diagnostic indicators, fluid sensors, temperature sensors, ignition sensors, exhaust monitoring, voltage sensors, and similar monitoring equipment that indicates when maintenance is required. Sensor displays are often located in inaccessible locations that cannot be observed during normal operation. Labor-intensive periodic maintenance is often required to inspect indicators. Some organizations have eliminated most labor-intensive periodic maintenance and diagnostic down time by implementing designs that bring all sensor status to fault indicators located in close proximity to users. 抄文引用元・出典: フリー百科事典『 ウィキペディア（Wikipedia）』 ■ウィキペディアで「Fault reporting」の詳細全文を読む スポンサード リンク
|